Securing asynchronous client server transactions

ABSTRACT

A system, and computer usable program product for securing asynchronous client server transactions are provided in the illustrative embodiments. A request including an application identifier and a version of a second application is received at a first application. A service identifier is generated if a session with the second application is valid. A registry is generated at the first application. A catalog is generated based on the registry and the service identifier and the catalog are sent to the second application. A sub-request including the service identifier is received as part of an asynchronous client server transaction. Validity of the sub-request is determined by determining whether the service identifier has expired, whether the sub-request requests a service that is permissible according to the catalog, whether the service identifier is used in conjunction with the second application, or a combination thereof. If the sub-request is valid, the service is provided.

BACKGROUND OF THE INVENTION

1. Field of the Invention

The present invention relates generally to an improved data processingsystem, and in particular, to providing data security. Still moreparticularly, the present invention relates to a system, and computerusable program code for securing asynchronous client servertransactions.

2. Description of the Related Art

Data is frequently exchanged between various data processing systemsusing one or more data networks. Some data processing systems may beregarded as client data processing systems in that they are consumers ofdata or services. Other data processing systems may be regarded asserver data processing systems in that they provide the requested dataor services. Applications executing as clients, to wit, as consumers ofdata or services, are called client applications. Applications executingas servers, to wit, providing data or services, are called serverapplications.

Security of the data, the systems the data resides on, and the networkswhere the systems operate, is a concern in data communications.Typically, security of a data processing system, contents thereof, andnetworks that the data processing system operates on is accomplished bysome security mechanism. A user identifier (UID) and passwordauthentication is a common method of accomplishing security objectivesin data processing environments.

Client and server data processing systems may communicate with eachother using a variety of protocols. Data communication occurring betweena client and a server data processing system includes a series ofrequests and responses. Requests and responses that are related to oneanother form a transaction.

Security of the client server transactions is presently achieved in avariety of ways. Certain protocols, such as HyperText Transfer ProtocolSecure (HTTPS) accomplish security of the client server transactions byusing encryption and secure identification of the server data processingsystem. Certain other transaction security mechanisms include usingsession identifiers (session ID). A session ID is an identifier used toidentify a session between a client and a server data processing system.A typical session may include a series of transactions.

In some cases, a client may request data from a server asynchronously.Asynchronous data transfer is transferring data without interfering withthe behavior of an ongoing task. For example, a web browser applicationmay be a client application. The web browser may request data from a webserver asynchronously such that the behavior or the display of a pagebeing displayed in the web browser is not affected by the asynchronousdata request or response. An asynchronous request also does not wait fora corresponding response. In other words, a response to an asynchronousrequest may arrive and be processed at the client at any time. Theclient does not wait for a response to an asynchronous request, butcontinues to work on other tasks.

An asynchronous request is a request for asynchronous data or service.An asynchronous client server transaction is a client server transactionoccurring asynchronously with respect to another ongoing task.

Asynchronous JavaScript and XML (AJAX) is a technology presently usedfor creating and performing asynchronous client server transactions.Asynchronous client server transactions are particularly useful inimproving the performance of the web applications and in improving userexperience.

SUMMARY OF THE INVENTION

The illustrative embodiments provide a system, and computer usableprogram product for securing asynchronous client server transactions. Anembodiment receives a request at a first application executing in a dataprocessing system. The request includes an application identifier and aversion associated with a second application. The embodiment generates aservice identifier if a session with the second application is valid.The embodiment generates a registry at the first application. Theregistry includes information about a set of services and data that thesecond application is permitted to use. The embodiment generates acatalog based on the registry. The catalog includes a subset of thecontents, or some transformation thereof, of the registry. Theembodiment sends the service identifier and the catalog to the secondapplication.

Another embodiment further receives a sub-request. The sub-request is apart of an asynchronous client server transaction and includes theservice identifier. The embodiment determines the validity of thesub-request by determining whether the service identifier has expired,whether the sub-request requests a service that is permissible accordingto the catalog, whether the service identifier is used in conjunctionwith the second application, or a combination thereof. If thesub-request is valid, the embodiment provides the service in response tothe sub-request.

In another embodiment, the determining of the validity may furthercombine in the combination, determining whether the catalog is outdated.

In another embodiment, the determination whether the service identifieris used in conjunction with the second application includes determiningwhether the service identifier is used together with the applicationidentifier and the application version of the second application.

If the sub-request is invalid, another embodiment further provides arenewed service identifier, a renewed catalog, or a combination thereof.The sub-request may then be re-tried with the renewed serviceidentifier, renewed catalog, or a combination thereof.

In an embodiment, the renewed service identifier may be a new serviceidentifier, the service identifier including a modified securityfeature, the service identifier corresponding to a modification of thesecurity feature validation criterion at the first application, or acombination thereof. A sub-request may be re-tried with the renewedservice identifier. The providing in such an embodiment occurs beforethe asynchronous client server transaction is concluded.

In another embodiment, the renewed catalog may be a new catalog, anupdate to the catalog, a modification to an expiration parameter of thecatalog, or a combination thereof. A sub-request may be re-tried withthe renewed catalog. In such an embodiment, the providing occurs beforethe asynchronous client server transaction is concluded.

Another embodiment further determines whether the service requiresadditional authentication. If additional authentication is needed, theembodiment receives additional authentication information in response toa request for the additional authentication information. The embodimentdetermines whether the additional authentication information is valid.The embodiment provides the service if the additional authenticationinformation is valid.

In an embodiment, the determination whether the service is permissibleaccording to the catalog is performed by determining whether the serviceis permissible using the registry.

Another embodiment generates an original service identifier. In such anembodiment, the service identifier is a transformed version of theoriginal service identifier.

BRIEF DESCRIPTION OF THE DRAWINGS

The novel features believed characteristic of the invention are setforth in the appended claims. The invention itself; however, as well asa preferred mode of use, further objectives and advantages thereof, willbest be understood by reference to the following detailed description ofan illustrative embodiment when read in conjunction with theaccompanying drawings, wherein:

FIG. 1 depicts a pictorial representation of a network of dataprocessing systems in which illustrative embodiments may be implemented;

FIG. 2 depicts a block diagram of a data processing system in whichillustrative embodiments may be implemented;

FIG. 3 depicts a block diagram of a data processing environment in whichan illustrative embodiment may be implemented;

FIG. 4 depicts a block diagram of a server data processing systemconfiguration for securing asynchronous client server transactions inaccordance with an illustrative embodiment;

FIG. 5 depicts a block diagram of a configuration of a client dataprocessing system for securing asynchronous client server transactionsin accordance with an illustrative embodiment;

FIG. 6 depicts a timing diagram of transactions occurring within anasynchronous client server transaction in accordance with anillustrative embodiment;

FIG. 7 depicts a block diagram of a service identifier and catalogrenewal process in accordance with an illustrative embodiment;

FIG. 8 depicts a flowchart of a process of generating a registry, aservice identifier, and a catalog in accordance with an illustrativeembodiment;

FIG. 9 depicts a flowchart of a process of securing asynchronous clientserver transactions in accordance with an illustrative embodiment; and

FIG. 10 depicts a flowchart of another process of securing asynchronousclient server transactions in accordance with an illustrativeembodiment.

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENT

The invention recognizes that presently, a client may perform severalsub-requests under an asynchronous client server transaction. Using thepresently available technology for asynchronous client servertransactions, a client may authenticate once to the server and then makemultiple sub-requests and traverse various services the server mayoffer.

The invention recognizes that in this manner, the client may gain accessto services that may be unrelated to the transaction or the client'soperation. The invention further recognizes that malicious applicationsmay leverage a legitimate client's asynchronous client servertransaction to gain access to services and data at the server after theinitial authentication is successful.

The invention further recognizes that the session ID technique isinsufficient to prevent these types of transgressions. Session IDtechnique falls short because generally the session ID remains unchangedduring a session and is also easily guessed based on other sessionparameters. Other presently available technologies are also insufficientto prevent access to unrelated services and data and to preventhijacking of asynchronous client server transactions for malicious use.

The illustrative embodiments used to describe the invention generallyaddress and solve the above-described problems and other problemsrelated to security in asynchronous client server transactions. Theillustrative embodiments provide a computer usable program product, anddata processing system for securing asynchronous client servertransactions.

The illustrative embodiments are described with respect to certaintransactions, data, data structures, requests, and responses only asexamples. Such descriptions are not intended to be limiting on theinvention. For example, an illustrative embodiment described withrespect to an AJAX transaction may be applied to an asynchronous clientserver transaction using another comparable technology, format, orstandard in a similar manner within the scope of the invention.

Furthermore, the illustrative embodiments are described with respect tospecific client and server data processing systems and applications onlyfor the clarity of the description. Without departing the scope of theinvention, the illustrative embodiments may be implemented with respectto any type of data processing system, data, data source, or access to adata source, that may act as clients and servers. An embodiment of theinvention may be implemented with respect to any type of application,such as, for example, any type of client application, serverapplication, platform application, stand-alone application, or acombination thereof.

Application may further include data objects, code objects, encapsulatedinstructions, application fragments, services, and other types ofresources available in a data processing environment. For example, Java®object, an Enterprise Java Bean (EJB®), a servlet, or an applet may bemanifestations of an application with respect to which, within which, orusing which, the invention may be implemented. (Java, EJB, and otherJava related terminologies are registered trademarks of SunMicrosystems, Inc. in the United States and other countries.)

An illustrative embodiment may be implemented in hardware, software, ora combination thereof. The examples in this disclosure are used only forthe clarity of the description and are not limiting on the illustrativeembodiments. Additional or different information, data, operations,actions, tasks, activities, and manipulations will be conceivable fromthis disclosure for similar purpose and the same are contemplated withinthe scope of the illustrative embodiments.

The illustrative embodiments are described using specific identifiers,parameters, attributes, configurations, code, data structures, filesystems, designs, architectures, layouts, schematics, and tools only asexamples and are not limiting on the illustrative embodiments.Furthermore, the illustrative embodiments are described in someinstances using particular software tools and data processingenvironments only as an example for the clarity of the description. Theillustrative embodiments may be used in conjunction with othercomparable or similarly purposed structures, systems, applications, orarchitectures.

Any advantages listed herein are only examples and are not intended tobe limiting on the illustrative embodiments. Additional or differentadvantages may be realized by specific illustrative embodiments.Furthermore, a particular illustrative embodiment may have some, all, ornone of the advantages listed above.

With reference to the figures and in particular with reference to FIGS.1 and 2, these figures are example diagrams of data processingenvironments in which illustrative embodiments may be implemented. FIGS.1 and 2 are only examples and are not intended to assert or imply anylimitation with regard to the environments in which differentembodiments may be implemented. A particular implementation may makemany modifications to the depicted environments based on the followingdescription.

FIG. 1 depicts a pictorial representation of a network of dataprocessing systems in which illustrative embodiments may be implemented.Data processing environment 100 is a network of computers in which theillustrative embodiments may be implemented. Data processing environment100 includes network 102. Network 102 is the medium used to providecommunications links between various devices and computers connectedtogether within data processing environment 100. Network 102 may includeconnections, such as wire, wireless communication links, or fiber opticcables. Server 104 and server 106 couple to network 102 along withstorage unit 108. Software applications may execute on any computer indata processing environment 100.

In addition, clients 110, 112, and 114 couple to network 102. A dataprocessing system, such as server 104 or 106, or client 110, 112, or 114may contain data and may have software applications or software toolsexecuting thereon.

Server 104 may include application server 105. Application server 105may be any application operating to serve other applications andservices. Server 106 may include service 107. Service 107 may be afunction, operation, or an application that may manipulate data, servedata, or perform a combination thereof. Client 112 may include clientapplication 113. Client application 113 may be an application or acomponent thereof, capable of conducting asynchronous client servertransactions according to an embodiment of the invention.

Servers 104 and 106, storage unit 108, and clients 110, 112, and 114 maycouple to network 102 using wired connections, wireless communicationprotocols, or other suitable data connectivity. Clients 110, 112, and114 may be, for example, personal computers or network computers.

In the depicted example, server 104 may provide data, such as bootfiles, operating system images, and applications to clients 110, 112,and 114. Clients 110, 112, and 114 may be clients to server 104 in thisexample. Clients 110, 112, 114, or some combination thereof, may includetheir own data, boot files, operating system images, and applications.Data processing environment 100 may include additional servers, clients,and other devices that are not shown.

In the depicted example, data processing environment 100 may be theInternet. Network 102 may represent a collection of networks andgateways that use the Transmission Control Protocol/Internet Protocol(TCP/IP) and other protocols to communicate with one another. At theheart of the Internet is a backbone of data communication links betweenmajor nodes or host computers, including thousands of commercial,governmental, educational, and other computer systems that route dataand messages. Of course, data processing environment 100 also may beimplemented as a number of different types of networks, such as forexample, an intranet, a local area network (LAN), or a wide area network(WAN). FIG. 1 is intended as an example, and not as an architecturallimitation for the different illustrative embodiments.

Among other uses, data processing environment 100 may be used forimplementing a client server environment in which the illustrativeembodiments may be implemented. A client server environment enablessoftware applications and data to be distributed across a network suchthat an application functions by using the interactivity between aclient data processing system and a server data processing system. Dataprocessing environment 100 may also employ a service orientedarchitecture where interoperable software components distributed acrossa network may be packaged together as coherent business applications.

With reference to FIG. 2, this figure depicts a block diagram of a dataprocessing system in which illustrative embodiments may be implemented.Data processing system 200 is an example of a computer, such as server104 or client 110 in FIG. 1, in which computer usable program code orinstructions implementing the processes may be located for theillustrative embodiments.

In the depicted example, data processing system 200 employs a hubarchitecture including North Bridge and memory controller hub (NB/MCH)202 and south bridge and input/output (I/O) controller hub (SB/ICH) 204.Processing unit 206, main memory 208, and graphics processor 210 arecoupled to north bridge and memory controller hub (NB/MCH) 202.Processing unit 206 may contain one or more processors and may beimplemented using one or more heterogeneous processor systems. Graphicsprocessor 210 may be coupled to the NB/MCH through an acceleratedgraphics port (AGP) in certain implementations.

In the depicted example, local area network (LAN) adapter 212 is coupledto south bridge and I/O controller hub (SB/ICH) 204. Audio adapter 216,keyboard and mouse adapter 220, modem 222, read only memory (ROM) 224,universal serial bus (USB) and other ports 232, and PCI/PCIe devices 234are coupled to south bridge and I/O controller hub 204 through bus 238.Hard disk drive (HDD) 226 and CD-ROM 230 are coupled to south bridge andI/O controller hub 204 through bus 240. PCI/PCIe devices may include,for example, Ethernet adapters, add-in cards, and PC cards for notebookcomputers. PCI uses a card bus controller, while PCIe does not. ROM 224may be, for example, a flash binary input/output system (BIOS). Harddisk drive 226 and CD-ROM 230 may use, for example, an integrated driveelectronics (IDE) or serial advanced technology attachment (SATA)interface. A super I/O (SIO) device 236 may be coupled to south bridgeand I/O controller hub (SB/ICH) 204.

An operating system runs on processing unit 206. The operating systemcoordinates and provides control of various components within dataprocessing system 200 in FIG. 2. The operating system may be acommercially available operating system such as Microsoft® Windows®(Microsoft and Windows are trademarks of Microsoft Corporation in theUnited States and other countries), or Linux® (Linux is a trademark ofLinus Torvalds in the United States and other countries). An objectoriented programming system, such as the Java™ programming system, mayrun in conjunction with the operating system and provides calls to theoperating system from Java™ programs or applications executing on dataprocessing system 200 (Java is a trademark of Sun Microsystems, Inc., inthe United States and other countries).

Instructions for the operating system, the object-oriented programmingsystem, and applications or programs are located on storage devices,such as hard disk drive 226, and may be loaded into main memory 208 forexecution by processing unit 206. The processes of the illustrativeembodiments may be performed by processing unit 206 using computerimplemented instructions, which may be located in a memory, such as, forexample, main memory 208, read only memory 224, or in one or moreperipheral devices.

The hardware in FIGS. 1-2 may vary depending on the implementation.Other internal hardware or peripheral devices, such as flash memory,equivalent non-volatile memory, or optical disk drives and the like, maybe used in addition to or in place of the hardware depicted in FIGS.1-2. In addition, the processes of the illustrative embodiments may beapplied to a multiprocessor data processing system.

In some illustrative examples, data processing system 200 may be apersonal digital assistant (PDA), which is generally configured withflash memory to provide non-volatile memory for storing operating systemfiles and/or user-generated data. A bus system may comprise one or morebuses, such as a system bus, an I/O bus, and a PCI bus. Of course, thebus system may be implemented using any type of communications fabric orarchitecture that provides for a transfer of data between differentcomponents or devices attached to the fabric or architecture.

A communications unit may include one or more devices used to transmitand receive data, such as a modem or a network adapter. A memory may be,for example, main memory 208 or a cache, such as the cache found innorth bridge and memory controller hub 202. A processing unit mayinclude one or more processors or CPUs.

The depicted examples in FIGS. 1-2 and above-described examples are notmeant to imply architectural limitations. For example, data processingsystem 200 also may be a tablet computer, laptop computer, or telephonedevice in addition to taking the form of a PDA.

With reference to FIG. 3, this figure depicts a block diagram of a dataprocessing environment in which an illustrative embodiment may beimplemented. Client data processing system 302 may be similar to client112 in FIG. 1. Client application 304 may be similar to clientapplication 113 in FIG. 1. Server data processing system 306 may besimilar to server 104 in FIG. 1. Application server 308 may be similarto application server 105 in FIG. 1.

As with presently used asynchronous client server transactionstechnology, client application 304 may make an initial asynchronousrequest to application server 308 followed by one or more sub-requests.The sub-requests may be for utilizing authorized service 310, accessingauthorized data 312, or both.

As an example, malicious application 314 may be an application on clientdata processing system 302 that may spoof the transaction informationbetween client application 304 and application server 308 and makesub-requests that may allow malicious application 314 access toprotected service 316, protected data 318, or both.

Note that malicious application 314 may be any application with anypurpose but behaving in this manner. In fact, under certaincircumstances, client application 302 may itself behave as maliciousapplication 314 and access protected resources in this manner.

Authorized service 310 and authorized data 312 may be any service ordata that may be legitimately accessed by client application 302 under agiven asynchronous client server transaction. Protected service 316 andprotected data 318 are examples of services or data available on serverdata processing system 306 that may be beyond the scope of a givenasynchronous client server transaction.

With reference to FIG. 4, this figure depicts a block diagram of aserver data processing system configuration for securing asynchronousclient server transactions in accordance with an illustrativeembodiment. Server data processing system 402 may be implemented usingserver data processing system 306 in FIG. 3. Application server 404 maybe implemented using application server 308 in FIG. 3.

Application server 404 utilizes authentication engine 406 toauthenticate an initial request that may be received from a clientapplication in connection with an asynchronous client servertransaction. Typically, the initial request includes an applicationidentifier associated with the client application, and an applicationversion of the client application. The initial request may also includeany user authentication credentials, such as a user identifier and apassword.

According to an illustrative embodiment, authentication engine 406authenticates the client application, the user, if any. Upon successfulauthentication, authentication engine 406 provides information toapplication server 404 that enables application server 404 to createregistry 408.

Registry 408 is a listing of activities the client application isauthorized to perform on server data processing system 402. For example,registry 408 may include identifiers or parameters of a set of servicesavailable on server data processing system 402 that the authenticatedclient application may access. A set of services is one of moreservices.

As another example, registry 408 may include parameters specifyingportions of a database that the authenticated client application mayquery. As another example, registry 408 may include negative parametersor identifiers, that is, parameters or identifiers of a set of servicesand data that the authenticated client application is prohibited fromusing. A set of services and data is one or more services or data.

These example entries in registry 408 are described only for the clarityof the illustrative embodiment and are not limiting on the invention.Many other types of similarly purposed information may be recorded inregistry 408 within the scope of the invention.

Upon authenticating the client application, authentication engine 406 incombination with application server 404 generates service identifier(service ID) 410. Service identifier 410 is a unique identifier that isassociated with the asynchronous client server transaction or a partthereof.

Application server 404 returns service identifier 410 and catalog 412 tothe authenticated client application in response to the clientapplication's initial request. Catalog 412 includes a subset of thecontents of registry 408. In one embodiment, catalog 412 may includesome or all of the information of registry 408 in a format or datastructure different from that in registry 408. In other words, thecontents of catalog 412 may be similar to, or a transformation of, someor all of the contents of registry 408, as shown by block 414.

Block 414 represents some or all of the contents of registry 408 thatmay be used to construct catalog 412. In one embodiment, contents ofblock 414 may appear in an unchanged form in catalog 412. In anotherembodiment, contents of block 414 may be transformed, such as bycompression, encryption, or reorganization, when they appear in catalog412.

In one embodiment, service identifier 410 may be associated with certainsecurity features. For example, service identifier 410 may be valid onlyfor a predetermined period during the asynchronous client servertransaction and may have to be renewed thereafter. As another example,service identifier 410 may be valid only for a predetermined number ofsub-requests in the asynchronous client server transaction and may haveto be renewed thereafter.

Any other security features, such as encryption, as may be suitable fora particular implementation, may be applied to service identifier 410within the scope of the invention. The operation and the nature ofservice identifier 410 are described in detail with respect to FIGS. 6and 7.

In an embodiment, catalog 412 may be dynamic in nature. In other words,contents of catalog 412 may change during the asynchronous client servertransaction for which catalog 412 is created. For example, in oneembodiment, catalog 412 may remain valid only for a predetermined periodand may have to be refreshed thereafter. As another example, in anotherembodiment, catalog 412 may contain only information sufficient forcertain types or number of anticipated sub-requests, and may have to berefreshed or renewed thereafter with information for additional types ornumber of sub-requests.

These example configurations of catalog 412 are not intended to belimiting on the invention. Any other security features, such asencryption, as may be suitable for a particular implementation, may beapplied to catalog 412 within the scope of the invention. The operationand the nature of catalog 412 are described in detail with respect toFIGS. 6 and 7.

Application server 404, authentication engine 406, and registry 408 areshown to be within server data processing system 402 only as an exampleconfiguration. An implementation of an embodiment of the invention maydistribute these components across different data processing systems inany combination in a data processing environment within the scope of theinvention.

With reference to FIG. 5, this figure depicts a block diagram of aconfiguration of a client data processing system for securingasynchronous client server transactions in accordance with anillustrative embodiment. Client data processing system 502 may beimplemented using client data processing system 302 in FIG. 3. Clientapplication 504 may be implemented using client application 304 in FIG.3. Malicious application 506 may be analogous to malicious application314 in FIG. 3. Service identifier 508 may be implemented using serviceidentifier 410 in FIG. 4. Catalog 510 may be implemented using catalog412 in FIG. 4.

Client application 504 may transmit an initial request to an applicationserver for an asynchronous client server transaction, as described withrespect to FIG. 4. Client application 504 may include applicationidentifier 512 and application version 514 associated with clientapplication 504 in the request. Optionally, client application 504 mayalso include authentication information associated with a user, if any.Upon successful authentication using the authentication information ofthe request at the application server, in response to the request,client application 504 receives service identifier 508 and catalog 510.

In one embodiment, client application 504 may also receive presentlyused identifiers and information, such as a session identifier. Asdescribed above, malicious application 506 may be able to guess or spoofsuch presently used identifiers and information. However,advantageously, the structure and manner of use of service identifier508 and catalog 510 in continuing the asynchronous client servertransaction are not susceptible to use by malicious application 506 in asimilar manner.

In one embodiment, a combination of application identifier 512,application version 514, service identifier 508, and contents of catalog510 are used in a sub-request. This combination is used in dynamicallycreating the sub-request according to an embodiment as opposed to fixedor pre-coded sub-requests as in the present art. The dynamicconstruction of the sub-requests, and the combination of applicationidentifier 512, application version 514, service identifier 508, andcontents of catalog 510 allow an embodiment of the invention to achievesecurity of the asynchronous client server transaction and thesub-requests therein that is not possible with the presently availabletechnology for asynchronous client server transactions.

With reference to FIG. 6, this figure depicts a timing diagram oftransactions occurring within an asynchronous client server transactionin accordance with an illustrative embodiment. Client application 602may be implemented using client application 502 in FIG. 5. Applicationserver 604 may be implemented using application server 404 in FIG. 4.

Application server component 606 may be an application, engine, or acomponent utilized by application server 604. For example, in oneembodiment, application server component 606 may be a combination ofauthentication engine 406 in FIG. 4 and certain other existingcomponents of a presently available application server application.Application server component 606 may be more than one application servercomponents serving different functions.

In one example embodiment, application server 604 may present logindialog 607 to client application 602. Login dialog 607 may be optional,and client application 602 may provide authentication credentials inrequest 608 on its own initiative or in response to login dialog 607.Authentication credentials may include a combination of an applicationidentifier associated with client application 602, an applicationversion associated with client application 602, an identifier associatedwith request 608, and one or more authentication credentials associatedwith a user or account, if any.

Application server 604 uses the authentication credentials in request608 to validate the session with client application 602. In oneembodiment, application server 604 may send validate session message 610to application server component 606 and receive a validation messageback to accomplish this validation.

Application server 604 may use application server component 606 togenerate services registry 612. Services registry generated in step 612may be used as registry 408 in FIG. 4 and may include description ofservices as well as data or other resources available throughapplication server 604.

Application server component 606 generates service identifier 614.Service identifier generated in step 614 may be used as serviceidentifier 410 in FIG. 4 and service identifier 508 in FIG. 5.

Application server 604 sends response 616 to client application 602. Oneor more messages may form response 616. Response 616 communicates theservice identifier and a catalog to client application 602. Catalog inresponse 616 may be a subset of services registry generated in step 612.Catalog in response 616 may be used as catalog 412 in FIG. 4 and catalog510 in FIG. 5.

Client application 602 may send one or more sub-requests to applicationserver 604. Sub-request for service or data 618 is one such sub-request.

Client application 602 constructs sub-request 618 dynamically using theservice identifier and catalog received in response 616. For example, inone embodiment, sub-request 618 may include a request for only thatservice which occurs in the catalog received in response 616.Sub-request 618 in an embodiment may further include the applicationidentifier of client application 602, application version of clientapplication 602, the service identifier received in response 616 or atransformation of such service identifier.

Thus, as different from the presently used techniques for asynchronousclient server transactions, an embodiment of the invention secures theasynchronous client server transaction by creating sub-requests whenneeded using information from the catalog and the service identifier,both of which may change over time. Creating the sub-requests in thismanner makes the sub-request dynamic and resistant to spoofing ortrial-and-error attacks by malicious applications.

Application server 604 performs service identifier expiration check 620,such as by using application server component 606. An embodiment mayperform check 620 after each sub-request 618. Another embodiment mayperform check 620 after several sub-requests according to a policy oralgorithm of choice.

Time based expiry of service identifier is only used as an example inthis embodiment and is not limiting on the invention. Any securityfeature related to the service identifier may be checked in a suitablemanner in step 620 within the scope of the invention.

If the service identifier has not expired, application server may sendrequest 622 to application server component 606 for the service or datarequested in sub-request 618. Application server 604 may send furtherrequest 624 to application server component 606 for any additional dataprocessing that may have to be performed using a combination of theservice identifier, the application identifier, and the applicationversion. For example, request 624 may be for logging sub-request 618. Asanother example, request 624 may be for incrementing an expiration countof the service identifier.

Application server 604 collects 626 the data or service requested byclient application 602. Application server 604 sends 628 the data orservice to client application 602.

Some steps of the timing diagram of FIG. 6 may occur more than once inan asynchronous client server transaction that is secured by anembodiment in this manner. For example, application server 604 may sendanother response 616 including renewed service identifier, refreshedcatalog, or both if check 620 detects that the service identifier insub-request 618 has expired.

Activities depicted as being performed at application server component606 as so depicted only as examples for the clarity of the description.Such activities may be performed at application server 604 or one ormore application server components 606 within the scope of theinvention.

With reference to FIG. 7, this figure depicts a block diagram of aservice identifier and catalog renewal process in accordance with anillustrative embodiment. Client application 702 may be similar to clientapplication 602 in FIG. 6. Application server 704 may be similar toapplication server 604 in FIG. 6. Application server component 706 maybe similar to application server component 606 in FIG. 6.

In one example embodiment according to FIG. 7, client application 702sends initial request 708 to application server 704. Application servercomponent 706 generates a registry and a service identifier. Applicationserver 704 returns a catalog based on the registry, and the serviceidentifier to client application 702.

Client application 702 constructs sub-requests dynamically using thecatalog and the service identifier and other information associated withclient application 702 and the asynchronous client server transaction.Client application 702 sends one or more such dynamically constructedsub-requests in furtherance of the asynchronous client servertransaction.

The service identifier expires or otherwise becomes invalid at clientapplication 702 at some point in time. For example, the serviceidentifier may expire before the asynchronous client server transactionis complete, forcing the use of multiple service identifiers to completethe asynchronous client server transaction. As another example, theservice identifier may expire at a certain time whether or not theasynchronous client server transaction has been completed.

Application server 704 may validate the service identifier and othercredentials in any combination at in any manner suitable to animplementation. For example, in one embodiment, application servercomponent 706 may validate the service identifier in each sub-request.In another embodiment, the service identifier may be validated at presetintervals. In another embodiment, the service identifier may bevalidated together with another authentication credential.

Validation of the service identifier may include any type of validationsuitable for an implementation. For example, one validation may checkfor the integrity of the service identifier to determine whether theservice identifier has been modified. Another example validation maysimply check for the expiration of the service identifier. Anotherexample validation may check to determine whether an otherwise validservice identifier is being used with the same application identifierwith which the service identifier was correlated at issuance or adifferent application identifier.

In one embodiment, client application 702 sends a dynamicallyconstructed sub-request with an expired service request. The expiredservice identifier fails validation at application server component 706.Application server 704 sends a new or renewed service identifier toclient application 702, if such renewal is warranted. For example,application server 704 may not send a renewed service identifier ifclient application 702 has taken more than a preset amount of time tocomplete an asynchronous client server transaction. The catalog atclient application 702 may similarly expire, become outdated, orotherwise become invalid. Application server 740 may similarly renew orrefresh the catalog, if warranted.

Client application 702 dynamically constructs subsequent sub-requestsusing the renewed service identifier, the renewed catalog, or both. Themessaging and communication between client application 702 andapplication server 704 may continue in this manner until the securedasynchronous client server transaction is concluded.

With reference to FIG. 8, this figure depicts a flowchart of a processof generating a registry, a service identifier, and a catalog inaccordance with an illustrative embodiment. Process 800 may beimplemented in a server application, such as in a combination ofapplication server 704 and application server component 706 in FIG. 7.

Process 800 begins by receiving a request (step 802). Request in step802 may be an initial request simply identifying an application, or maybe a request for service or data.

Process 800 detects an application identifier and an application versionfrom the request of step 802 (step 804). If process 800 determines thatconnectivity with the sender of the request is acceptable (not shown),process 800 generates a service identifier (step 806).

Process 800 also generates a registry of services, data, or acombination thereof, that the sender of the request may be allowed touse (step 808). Process 800 updates the registry with the serviceidentifier and any other authentication credentials from the request(step 810).

Process 800 generates a catalog of services and data based on theregistry (step 812). Process 800 sends the service identifier and thecatalog in response to the request of step 802 (step 814). Process 800ends thereafter.

With reference to FIG. 9, this figure depicts a flowchart of a processof securing asynchronous client server transactions in accordance withan illustrative embodiment. Process 900 may be implemented in a serverapplication, such as in application server 704, application servercomponent 706, or a combination thereof, in FIG. 7.

Process 900 begins by receiving a request that includes a combination ofan application identifier, an application version, and a serviceidentifier (step 902). The request of step 902 may be similar to asub-request of FIG. 7. The service identifier may be similar to theservice identifier sent in step 814 in FIG. 8.

Process 900 determines whether the service identifier is expired orotherwise valid, whether the catalog at the sender of the request has tobe updated, or both (step 904). If process 900 determines that theservice identifier has expired, or the catalog at the sender is out ofdate (“YES” path of step 904), process 900 determines whether to renewthe service identifier, the catalog, or both (step 906).

If process 900 determines not to renew the service identifier, thecatalog, or both (“NO” path of step 906), process 900 may log therequest (step 908). Process 900 may also send an error message to thesender of the request (step 910). Process 900 ends thereafter.

If process 900 determines to renew the service identifier, the catalog,or both (“YES” path of step 906), process 900 may generate a new serviceidentifier or extend the expiration period of the existing serviceidentifier (step 912). Process 900 may also, if needed, generate a newcatalog, generate an update for the existing catalog, or extend thevalidity of the existing catalog (step 914). Process 900 sends the newor renewed service identifier, new or updated catalog, or both asneeded, in response to the request of step 902 (step 916). Process 900ends thereafter.

If at step 904, process 900 determines that service identifier is validand the catalog is up-to-date (“NO” path of step 904), process 900determines whether the session with the sender of the request is valid(step 918). If process 900 determines that the session with the senderof the request is invalid, such as when the service identifier or itsuse is invalid, or when a request is for a service not in the catalog(“NO” path of step 912), process 900 proceeds to step 908. Whether arequested service is in the catalog can be determined, for example, byexamining that portion of the registry that was included in the catalog.

If process 900 determines that the session with the sender of therequest is valid (“YES” path of step 918), process 900 determineswhether the requested service or data requires additional authentication(step 920). For example, certain services may require their own login IDand password.

If process 900 determines that additional authentication is needed(“YES” path of step 920), process 900 sends additional authenticationmessage, such as by presenting a login dialog box at a display (step922). Process 900 receives additional authentication information (step924).

Process 900 determines whether the additional authentication informationis valid (step 926). If the additional authentication information is notvalid (“NO” path of step 926), process 900 proceeds to step 908.

If the additional authentication information is valid (“YES” path ofstep 926), or if no additional authentication information is required bythe service requested (“NO” path of step 920), process 900 provides theservice or the data requested (step 928). Process 900 sends the resultof the service performed or the data manipulated according to therequest (step 930). Process 900 ends thereafter. The results may be sentto the sender of the request or to another application or device withoutdeparting the scope of the invention.

With reference to FIG. 10, this figure depicts a flowchart of anotherprocess of securing asynchronous client server transactions inaccordance with an illustrative embodiment. Process 1000 may beimplemented in a client application, such as client application 702 inFIG. 7.

Process 1000 begins by sending a request (step 1002). The request may besimilar to the request received in step 802 of process 800 in FIG. 8.

If the request is valid according to a receiver of the request (notshown), process 1000 receives a service identifier and a catalog (step1004). Process 1000 dynamically constructs one or more sub-requests forservice or data using the service identifier and the catalog (step1006). Process 1000 may also include additional authenticationcredentials in the sub-requests.

Process 1000 send the dynamically created sub-request (step 1008). Inresponse to the sub-request of step 1008, process 1000 may receive acombination of service or data requested (step 1010), renewed serviceidentifier or catalog (step 1012), and an error message (step 1014).Process 1000 ends thereafter.

The components in the block diagrams and the steps in the flowchartsdescribed above are described only as examples. The components and thesteps have been selected for the clarity of the description and are notlimiting on the illustrative embodiments of the invention. For example,a particular implementation may combine, omit, further subdivide,modify, augment, reduce, or implement alternatively, any of thecomponents or steps without departing from the scope of the illustrativeembodiments. Furthermore, the steps of the processes described above maybe performed in a different order within the scope of the invention.

Thus, an apparatus, and computer program product are provided in theillustrative embodiments for securing asynchronous client servertransactions. Using the embodiments of the invention, asynchronousclient server transactions can be secured in a manner that unrelatedservices are not accessible during an asynchronous client servertransaction. A requestor of an asynchronous client server transaction islimited to certain services and data that the provider determinespermissible.

The invention further provides the requestor of the asynchronous clientserver transaction ability to dynamically construct requests within theasynchronous client server transaction using provider-suppliedinformation. The combination of requestor's own information,provider-supplied information, and limitation on which service and datamay be requested secures the asynchronous client server transactionaccording to the embodiments of the invention. The nature of the serviceidentifier, the combination of the service identifier with otheridentifiers, and the expiration and renewal of the service identifieraccording to the embodiments make the asynchronous client servertransaction resistant to spoofing or trial-and error attacks.

The embodiments of the invention provide flexible securityconfigurations that can be changed or updated as needed. The embodimentsof the invention further provide security mechanism that does notrequire additional hardware and can work in existing hardware-softwareconfiguration of most existing data processing systems.

The embodiments of the invention can collaborate with existingauthentication applications and components. The embodiments can alsocollaborate with existing policy infrastructures that may be in use incertain data processing environments.

The invention can take the form of an entirely software embodiment, oran embodiment containing both hardware and software elements. In apreferred embodiment, the invention is implemented in software orprogram code, which includes but is not limited to firmware, residentsoftware, and microcode.

Furthermore, the invention can take the form of a computer programproduct accessible from a computer-usable or computer-readable mediumproviding program code for use by or in connection with a computer orany instruction execution system. For the purposes of this description,a computer-usable or computer-readable medium can be any tangibleapparatus that can contain, store, communicate, propagate, or transportthe program for use by or in connection with the instruction executionsystem, apparatus, or device.

The medium can be an electronic, magnetic, optical, electromagnetic,infrared, or semiconductor system (or apparatus or device) or apropagation medium. Examples of a computer-readable medium include asemiconductor or solid state memory, magnetic tape, a removable computerdiskette, a random access memory (RAM), a read-only memory (ROM), arigid magnetic disk, and an optical disk. Current examples of opticaldisks include compact disk-read only memory (CD-ROM), compactdisk-read/write (CD-R/W) and DVD.

Further, a computer storage medium may contain or store acomputer-readable program code such that when the computer-readableprogram code is executed on a computer, the execution of thiscomputer-readable program code causes the computer to transmit anothercomputer-readable program code over a communications link. Thiscommunications link may use a medium that is, for example withoutlimitation, physical or wireless.

A data processing system suitable for storing and/or executing programcode will include at least one processor coupled directly or indirectlyto memory elements through a system bus. The memory elements can includelocal memory employed during actual execution of the program code, bulkstorage media, and cache memories, which provide temporary storage of atleast some program code in order to reduce the number of times code mustbe retrieved from bulk storage media during execution.

A data processing system may act as a server data processing system or aclient data processing system. Server and client data processing systemsmay include data storage media that are computer usable, such as beingcomputer readable. A data storage medium associated with a server dataprocessing system may contain computer usable code. A client dataprocessing system may download that computer usable code, such as forstoring on a data storage medium associated with the client dataprocessing system, or for using in the client data processing system.The server data processing system may similarly upload computer usablecode from the client data processing system. The computer usable coderesulting from a computer usable program product embodiment of theillustrative embodiments may be uploaded or downloaded using server andclient data processing systems in this manner.

Input/output or I/O devices (including but not limited to keyboards,displays, pointing devices, etc.) can be coupled to the system eitherdirectly or through intervening I/O controllers.

Network adapters may also be coupled to the system to enable the dataprocessing system to become coupled to other data processing systems orremote printers or storage devices through intervening private or publicnetworks. Modems, cable modem and Ethernet cards are just a few of thecurrently available types of network adapters.

The description of the present invention has been presented for purposesof illustration and description, and is not intended to be exhaustive orlimited to the invention in the form disclosed. Many modifications andvariations will be apparent to those of ordinary skill in the art. Theembodiment was chosen and described in order to explain the principlesof the invention, the practical application, and to enable others ofordinary skill in the art to understand the invention for variousembodiments with various modifications as are suited to the particularuse contemplated.

What is claimed is:
 1. A computer usable program product comprising acomputer usable storage device including computer usable code forsecuring asynchronous client server transactions, the computer usablecode comprising: computer usable code for receiving a request at a firstapplication executing in a data processing system, the request includingan application identifier and a version associated with a secondapplication; computer usable code for generating a service identifierresponsive to a session with the second application being valid;computer usable code for generating a registry at the first application,the registry including information about a set of services and data thatthe second application is permitted to use; computer usable code forgenerating a catalog based on the registry, the catalog including atransformed subset of the registry; computer usable code for sending theservice identifier and the catalog to the second application; computerusable code for receiving a sub-request, the sub-request being a part ofan asynchronous client server transaction, the sub-request including theservice identifier; computer usable code for determining a validity ofthe sub-request by determining a combination of (i) whether the serviceidentifier has expired, (ii) whether the sub-request requests a servicethat is permissible according to the catalog, and (iii) whether theservice identifier is used in conjunction with the second application;and computer usable code for providing, responsive to the sub-requestbeing valid, the service in response to the sub-request.
 2. The computerusable program product of claim 1, wherein the determining the validityfurther uses in the combination (iv) determining whether the catalog isoutdated.
 3. The computer usable program product of claim 1, wherein thedetermination whether the service identifier is used in conjunction withthe second application comprises determining whether the serviceidentifier is used together with the application identifier and theapplication version of the second application.
 4. The computer usableprogram product of claim 1, further comprising: computer usable code forproviding, responsive to the sub-request being invalid, one of (i) arenewed service identifier, and (ii) a renewed catalog.
 5. The computerusable program product of claim 4, wherein the renewed serviceidentifier is one of (i) a new service identifier, (ii) the serviceidentifier including a modified security feature, and (iii) the serviceidentifier corresponding to a modification of the security featurevalidation criterion at the first application, and wherein the providingoccurs before the asynchronous client server transaction is concluded.6. The computer usable program product of claim 4, wherein the renewedcatalog is one of (i) a new catalog, (ii) an update to the catalog, and(iii) a modification to an expiration parameter of the catalog, andwherein the providing occurs before the asynchronous client servertransaction is concluded.
 7. The computer usable program product ofclaim 1, further comprising: computer usable code for determiningwhether the service requires additional authentication, forming adetermination of additional authentication; computer usable code forreceiving additional authentication information responsive to thedetermination of additional authentication being true; and computerusable code for determining whether the additional authenticationinformation is valid, wherein the service is provided responsive to theadditional authentication information being valid.
 8. The computerusable program product of claim 1, wherein the determination whether theservice is permissible according to the catalog by determining whetherthe service is permissible using the registry.
 9. The computer usableprogram product of claim 1, further comprising: computer usable code forgenerating an original service identifier, wherein the serviceidentifier is a transformed version of the original service identifier.10. The computer usable program product of claim 1, wherein the computerusable code is stored in a computer readable storage medium in a dataprocessing system, and wherein the computer usable code is transferredover a network from a remote data processing system.
 11. The computerusable program product of claim 1, wherein the computer usable code isstored in a computer readable storage medium in a server data processingsystem, and wherein the computer usable code is downloaded over anetwork to a remote data processing system for use in a computerreadable storage medium associated with the remote data processingsystem.
 12. A data processing system for securing asynchronous clientserver transactions, the data processing system comprising: a storagedevice including a storage medium, wherein the storage device storescomputer usable program code; and a processor, wherein the processorexecutes the computer usable program code, and wherein the computerusable program code comprises: computer usable code for receiving, froma first application, at a second application executing in a dataprocessing system, a service identifier and a catalog responsive tosending an application identifier and an application version associatedwith the second application, the catalog including a transformed subsetof a registry associated with the first application; computer usablecode for dynamically constructing a sub-request, the sub-request being apart of an asynchronous client server transaction, the sub-requestincluding the service identifier, and the sub-request further includinga request for a service from the catalog, wherein a validity of thesub-request is determinable by determining a combination of (i) whetherthe service identifier has expired, (ii) whether the sub-requestrequests a service that is permissible according to the catalog, and(iii) whether the service identifier is used in conjunction with thesecond application; and computer usable code for receiving, responsiveto the sub-request being valid according to the first application, dataassociated with the service.
 13. The data processing system of claim 12,wherein the sub-request further includes the application identifier andthe application version associated with the second application.
 14. Thedata processing system claim 12, further comprising: computer usablecode for receiving, responsive to the sub-request being invalid, one of(i) a renewed service identifier, and (ii) a renewed catalog, whereinthe sub-request is invalid due to a determination that one of (i) theservice identifier is invalid, (ii) the service is not within thecatalog, and (iii) the catalog is outdated; and computer usable code fordynamically constructing a second sub-request using one of (i) therenewed service identifier, and (ii) the renewed catalog.